Create service level compliance alert policies
Alerts can be generated when the performance of a storage group, relative to its service level target, changes.
Prerequisites
- See Roles and associated permissions to determine the user roles that can perform this task.
- The storage system must be registered for performance statistics collection.
- The storage group
- Must be either a child or stand-alone. Parent storage groups are not supported.
- Must be associated with a service level other than optimized.
- Must contain volumes other than gatekeepers.
- Must be in a masking view.
- Must not have a policy that is currently associated with it.
About this task
This procedure explains how to configure Unisphere to alert you when the performance of a storage group, relative to its service level target, changes. Once configured, Unisphere assesses the performance of the storage every 30 minutes, and determines the appropriate alert level.
When assessing the performance for a storage group, Workload Planner calculates its weighted response time for the past four hours and for the past two weeks, and then compares the two values to the maximum response time associated with its given service level. If both calculated values fall within (under) the service level defined response time band, the compliance state is STABLE. If one of them is in compliance and the other is out of compliance, then the compliance state is MARGINAL. If both are out of compliance, then the compliance state is CRITICAL.
The following table details the state changes that generate an alert and the alert level.
| State change | Alert generated | Alert level |
|---|---|---|
| ANY STATE > NONE | No | |
| NONE > STABLE | No | |
| NONE > MARGINAL | Yes | Warning |
| NONE > CRITICAL | Yes | Critical |
| STABLE > MARGINAL | Yes | Warning |
| STABLE > CRITICAL | Yes | Critical |
| STABLE > STABLE | No | |
| MARGINAL > STABLE | Yes | Info |
| MARGINAL > CRITICAL | Yes | Critical |
| MARGINAL > MARGINAL | No | |
| CRITICAL > STABLE | Yes | Info |
| CRITICAL > MARGINAL | Yes | Warning |
| CRITICAL > CRITICAL | Yes | Critical |
NOTE: When a storage group that is configured for compliance alerts is deleted or renamed, you must delete the compliance alerts. For instructions, see
Delete compliance alerts policies.
|
To create service level compliance alert policies:
Steps
-
Select
to open the
Settings panel.
- Click .
- Click Create.
- Select the storage system on which the storage groups are located.
- Select one or more storage groups and click >.
- Optional:
Compliance state settings can be configured using REST API. If the compliance
state settings have been configured as part of the system settings configuration
using REST API, these settings may not match the default settings. By default,
service level compliance policies are configured to generate alerts for all
service level compliance states. To change this default behavior, clear any of
the states for which you do not want to generate alerts:
Critical—Storage group performing well below service level targets. -
Marginal—Storage group performing below service level target. -
Stable—Storage group performing within the service level target.
- Click OK.